Optimizing data migration processes

ABSTRACT

Systems, methods, and apparatuses can present optimized data migration. Embodiments can provide improved data migration processes using a data migration assistant that executes on a source system to facilitate the migration of documents and data to a destination system. The migration assistant can communicate with a migration controller server to authenticate and identify the migration assistant and migration project that the migration assistant is to be used for. The migration controller server can use the identifier to determine commands corresponding to the migration project to send to the migration assistant to collect data and make changes to the source system.

CROSS-REFERENCES TO RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No.14/872,984, entitled “Optimizing Data Migration Processes,” filed Oct.1, 2015 , which is non-provisional of and claims priority to U.S.Provisional Application 62/058,605, entitled “Optimizing Data MigrationProcesses,” filed on Oct. 1, 2014 . The present application is alsorelated to U.S. Provisional Application 62/058,608, entitled “AutomatedStaged Data Migrations,” filed on Oct. 1, 2014 , and to concurrentlyfiled U.S. patent application entitled “Automated Staged DataMigrations,” which claims priority to U.S. Provisional Application62/058,605. The entire content of the above applications are herebyincorporated by reference for all purposes in its entirety.

BACKGROUND

The present disclosure relates to collecting and packaging data from asource system and sending commands to the source system to optimize datamigration from the source system.

Migration of data from a source system to a destination system isfraught with cost and obstacles. For example, those who are tasked withcarrying out the migration (referred to as “partners”) sometimes fail tofollow instructions, miss alerts, and/or simply carry out the migrationsteps incorrectly. Any of these events can have negative effects on amigration, resulting in lost data and additional expenses of money,man-hours, and system resources. Other problems exist with respect tocharacteristics and features of the source system that may be useful insome scenarios, but may also inhibit data migration.

Therefore, it is desirable to provide solutions that improve migrationactivities such as discovery of what is on the source server such asdata, email contents, users, permissions, and meta structure of thesource environment.

BRIEF SUMMARY

Embodiments can improve data migration processes using a data migrationassistant that executes on a source system to facilitate the migrationof documents to a destination system. The migration assistant executeson a computer of the source system. The migration assistant cancommunicate with a migration controller server. As part of anauthentication process (e.g., after installation of the migrationassistant), the migration assistant can send an identifier to amigration controller server. The identifier can identify the migrationproject that the migration assistant is to be used for. The migrationcontroller server can use the identifier to determine commandscorresponding to the migration project to send to the migrationassistant.

The migration assistant can query a source document server to collectmetadata from the source document server. The metadata corresponds todocuments stored on the source document server, e.g., documents that areto be migrated. In some embodiments, the query can be based oninstructions received from the migration controller server.

The migration assistant can establish a connection between the migrationassistant and the migration controller server using the identifier. Themetadata can be sent using the connection to the migration controllerserver. The migration assistant can receive one or more commands for themigration project from the migration controller server. The one or morecommands can specify changes to be made for the source document serveras part of the migration project. Once the migration assistantimplements the one or more changes, a confirmation can be sent to themigration controller server. Such changes can automatically prepare thesource document server for the migration, e.g., in a process that occursafter the migration assistant is installed.

Other embodiments are directed to systems, portable consumer devices,and computer readable media associated with methods described herein.

A better understanding of the nature and advantages of embodiments maybe gained with reference to this detailed description and theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of the architecture of a system formigrating data from a source system according to various embodiments.

FIG. 2 shows a block diagram for the installation, registration, andverification of a migration assistant according to embodiments of thepresent invention.

FIG. 3 shows a block diagram for the gathering of metadata (e.g.,inventory data) according to embodiments of the present invention.

FIG. 4 shows a block diagram for using a migration assistant executingat a source system for a migration project according to embodiments ofthe present invention.

FIG. 5 is a flow diagram of a migration process using a migrationassistant according to embodiments of the present invention.

FIG. 6 is a flow diagram of a cutoff migration according to variousembodiments.

FIG. 7 is a flow diagram of a staged migration according to variousembodiments.

FIG. 8 shows a block diagram of an example computer system 10 usablewith system and methods according to various embodiments.

TERMS

A migration project corresponds to a migration documents from aparticular source system to a particular destination system. Themigration project can be for only certain documents to be migrated,which may be defined in creation of a migration project. Multiplemigration projects can exist for a particular source system and aparticular destination system. Various documents can be migrated, suchas files and e-mails. A migration controller server can control amigration project.

A migration assistant executes on a computer of the source system andcan provide information to the migration controller server, where themigration controller server can use the information in controlling themigration of documents. The migration controller can send instructionsto the migration assistant specifying metadata to collect. The migrationassistant can perform actions according to commands received from themigration controller server. The migration controller can also providecommands to a migration engine that migrates the documents. In someimplementations, the migration may start after the migration assistanthas implemented commands specified by the migration controller. Detailsof a migration controller can be found in U.S. Patent Publication2013/0212200, which is incorporated by reference in its entirety.

An end user device of a source system can correspond to any user device(mobile or stationary) that does connect to the source system. The enduser device can be on a local network with the source system.

DETAILED DESCRIPTION

Problems related to migration of data from systems may vary depending onthe type of system involved, and each may require different solutions toaddress such problems. Such problems can stem from the human expertiserequired to complete complex server work, the need for precise timing ofchanges, the risk of error, complexity of the data being gathered, andthe architecture of the system itself. The solutions to these problemsprovided by some embodiments may be applied to multiple different typesof source systems, and certain examples in this application use aMicrosoft Exchange® Server program (hereinafter referred to as“Exchange”) in particular as an example for the purposes of illustrationand description. It is not intended to be exhaustive or to limitembodiments to the precise form described, as embodiments can be appliedto other systems.

To address such problems, embodiments (e.g., as implemented in amigration assistant) can gather (collect) an inventory of certainmetadata about documents in a source document server of a source system.For instance, metadata can be obtained about directory services andemail systems, for example in a Microsoft® Windows environment, Exchangeand Microsoft® Active Directory (a directory service implemented byMicrosoft® for Windows® domain networks). The term active directory canrefer to any directory that can provide certain information aboutdocuments stored in a source document server. The metadata can beobtained without a physical presence at the source system, i.e. withouta person having to manually perform operations at a computer of thesource system.

In various embodiments, as examples of part of the collection of themetadata, the migration assistant can discover email contents, settings,users, permissions, and other structures and data for a migration from asource system to a destination system by gathering data that wouldotherwise be inaccessible using the Internet, packaging gathered data ina single document for convenience of storage and processing related tothe migration to a destination system, automating various processes toreduce or eliminate the risk of human error, and sending commands to thesource system to avoid default behavior that would disrupt themigration. Accordingly, embodiments can improve the quality and accuracyof a migration by allowing for a closer configuration of a destinationenvironment to a source environment than would be obtainable without themigration assistant. The closer configuration can include for example,changing to an MEU from an on-premises mailbox, and generally make thedestination environment mirror the source environment as closely aspossible.

I. Introduction

FIG. 1 is a schematic diagram of the architecture of a system forcollecting and packaging metadata from a source system 136 to optimizedata migration from source system 136 to a destination system 118. Thecollection and packaging of the metadata may be performed by migrationassistant 124, which can received commands from a migration controllerserver 110. Migration assistant 124 is an application that can beinstalled on a server on the same local area network (depicted as sourceenvironment 120) as source system 136 (i.e. local to the location of thedata to be collected and migrated).

Migration assistant 124 can perform a deep inspection of source system136 and gather various metadata ((also referred to as “inventoryinformation”) about source system 136. For example, the deep inspectioncan determine daat such as the first name and last name of account,title of a user, and detailed permissions. Migration assistant 124 canalso receive commands from migration controller server 110, and performsthose commands, e.g., to make changes to source system 136 inpreparation for the migration to destination system 118.

As mentioned above, one problem with data migration is in the humanerror. Other problems also exist with respect to characteristics andfeatures of the source system 136 that may be useful in some scenarios,but may also inhibit data migration; consider the example of a datamigration from Microsoft Outlook® (an information manager that may beused with for example an Exchange® server like Document Server 128, andhereinafter referred to as “Outlook”) to an online-based service. AfterOutlook® has been reconfigured by the migration assistant to communicatewith the online-based service instead of the on-premise Exchange Server128, unless certain actions are taken in a timely manner, Outlook® canreconfigure itself back to the on-premise Exchange Server 128 it wasoriginally configured to. This can be problematic for the Outlook® userbecause they would be looking at their old non-online-based mailbox,which would no longer be receiving email sent to the user's emailaddress because the email would be delivered to the online-basedservice. Furthermore, if the Outlook® user sends an email, makes changesto online calendar appointments, or creates or modifies contacts, etc.,these changes will only apply to the old source mailbox since the sourcemailbox replication to the online-system had already been completed, andthus when Outlook® is fixed to communicate with the online-basedservice, these changes that the end user made will not be present in theonline-based service. Email is an example of a document that can bemigrated from a source system to a destination system.

One benefit of some embodiments is that it reduces or eliminates thehuman expertise required to complete the complex server work needed toavoid server behavior such as that outlined above. Another benefit ofsome embodiments is that the timing of changes to the source server canbe made with the required precision to enable for example asynchronization of data as close in time as possible during a migration,even for large-scale data migrations, in an automated fashion. The riskof error in carrying out data migrations may decrease dramatically dueto the above-listed benefits.

Another problem is that there are no solutions that gather an inventoryof certain data in a source system's Exchange 128 and Microsoft® ActiveDirectory 122 without a physical presence at the source system 136; suchdata may include, for example, details about the mailboxes of the sourcesystem 136 and its corresponding user, such as mailbox size, mailboxSMTP aliases, mailbox X500 addresses and aliases, mailbox legacyExchange ID, user's job title, user's office location, user'saddress(es), mailbox permissions, security groups the user is a memberof, etc. This data is not accessible remotely (via internet protocols orAPIs). As such, companies must choose whether to spend more money tohouse certain equipment locally to gather such data, or to foregocollection of that data and complete various steps manually followingthe migration. Some embodiments can use a Microsoft® technology calledPowerShell® (a task automation and configuration management framework)to retrieve this information from Active Directory 122 and Exchange 128.

It is also difficult to structure the collected data in a singledocument for convenience of storage and processing related to themigration. This is due to the fact that the data may be for many users,and may describe one-to-many relationships (e.g. a single mailbox withmultiple aliases) and many-to-many relationships (e.g. many securitygroups which each contain many users). A document containing this datamay contain many thousands of lines and relationships. Embodiments canuse XML to structure the data into a single document.

Accordingly, migration assistant 124 is installed local to the sourcesystem environment 120, which includes a document server 128 and activedirectory 122. Migration assistant 124 can communicate via connection126 with source document server 128 and active directory 122 to collectmetadata. The collected metadata may be sent to the migration controllerserver 110.

The migration controller server 110 can send commands to migrationassistant 124, and the migration assistant 124 can send commands toactive directory 122 and/or document server 128 to take various actions,both of which may report back status messages to the migration assistant124. The status messages may be viewed on a front end interface 104and/or administrative interface 114.

II. Installation, Registration, and Verification

In some embodiments, the migration assistant 124 may be installed localto the source system 136 and registered and verified with the migrationcontroller server 110; registration, verification, and othercommunications between the migration assistant 124 and the migrationcontroller server 110 take place over the internet, for example viapublicly accessible web services such as an API interface. These actionsmay occur as described below.

FIG. 2 shows a block diagram for the installation, registration, andverification of a migration assistant according to embodiments of thepresent invention. Migration assistant 124 may be downloaded locally andinstalled on a server on a local area network connected to the sourcesystem 136. The installation can require that the migration assistant belinked to the source server by providing a unique product key or otherregistration code. By using the unique product key when communicating,the migration assistant can be uniquely identified. This can provide aform of authentication for the migration assistant. FIG. 2 refers tocertain elements from FIG. 1.

Action 201 shows migration assistant 124 being downloaded from anapplication server 210. Application server 210 can be part of migrationcontroller environment 100 of FIG. 1, or may be a separate server.Migration assistant 124 may be downloaded at a computer of the sourcesystem by an administrator.

Action 202 shows an identifier being entered, e.g., by an administratorthat downloaded migration assistant 124. In one embodiment, theidentifier can be a registration code that corresponds to a migrationproject that has been registered with the migration controllerenvironment. The administrator can enter various information, such as aregistration code, a domain name of the domain being migrated, which canalso be called the order (project), a URL of the source document server,and credentials that have administrative access to the source documentserver. The information can be entered into a user interface by anoperator, which may be a local user interface provided by migrationassistant 124, or a web interface that migration assistant can access,such as front end interface 104.

The front end interface 104 is the user-facing front end of a projectmanagement application 102 used to manage and monitor data migrations;the project management application 102 may be web-based orapplication-based. An administrative user interface (UI) 114 may be usedfor administrative access to the project management application 102, forexample to allow for additional permissions to manage a migration. Thefront end interface 104 may include a web interface 106 and/or a mobileinterface 108.

Action 203 shows migration assistant 124 confirming access to sourcesystem 136. For example, after the registration code, domain name of themigration order (project), URL of the source document server, andcredentials can be entered by an operator, migration assistant 124 mayverify whether it can communicate with source system 136, andspecifically with the source document server. For example, migrationassistant 124 can confirm communication with a source email and userdatabases 138 through “PowerShell” or other task automation andconfiguration management framework.

Action 204 shows migration assistant 124 sending the identifier tomigration controller server 110. For example, if migration assistant 124is able to communicate with the source document server, migrationassistant 124 may send the registration code and domain name of theorder to a migration controller server 110. In some embodiments,migration controller server 110 may be a cloud server.

Action 205 shows migration controller server 110 sending anauthentication response to migration assistant 124. Migration controllerserver 110 may also send a success/failure response to migrationassistant 124 indicating whether or not migration controller server 110received the registration code and domain name of the order.

If the registration code and domain name of the order were received, themigration controller server 110 may perform a lookup in a migrationcontroller database 112 connected to the migration controller server 110to find a corresponding project identifier that the particular migrationassistant 124 is associated with. The project identifier can be a uniqueidentifier for each order. Migration controller server 110 may send asuccess/failure response to the migration assistant 124 indicatingwhether or not there was a match. If there was a match, migrationassistant 124 can enter a running state as an application or service,and the administrator or other user may be presented with confirmationof this via the front end interface 104 and/or administrative UI 114.

III. Inventory (Metadata) Gathering

In some embodiments, the migration assistant 124 can gather inventoryrelated to the source system 136. The inventory may include, but is notlimited to, the name of the Exchange server 128, a list of all clientaccess servers related to the source system 136, details about theclient access servers, information about the Active Directorycontroller, and results of a test of upload bandwidth between themigration assistant 124 and a data center local to the destinationsystem 118 (e.g. the Microsoft® Data Center). The client access serverscan comprise the servers that clients use to access their email. All ofthe data collected may be sent to the migration controller server 110,which analyzes the data to select and/or create various commands to besent back to the migration assistant 124 at a later time. The datacollected may comprise for example, mailboxes, distribution lists,names, phone numbers, any data that may be retrieved from the sourcesystem.

FIG. 3 shows a block diagram for the gathering of metadata (e.g.,inventory data) according to embodiments of the present invention. Themetadata can be collected from source system 136 using migrationassistant 124. The collection can be based on instructions frommigration controller server 110. FIG. 3 refers to certain elements fromFIG. 1.

Action 301 shows migration controller server 110 sending an instructionto collect metadata. For example, migration controller server 110 maysend migration assistant 124 an instruction to collect various businessrules from source document server 128 and active directory 122 local tosource system 136, which in effect establishes an inventory of thoseenvironments. Many of these business rules would not be accessible usingremote access methods. But with the aid of the migration assistant 124running on the local network of the source system 136, a local API(which may be provided by a third party) may be used to gather the data.

Action 302 shows migration assistant 124 querying source system 136 forthe specified metadata, which may include business rules. Business rulesthat may be collected include, but are not limited to, user mailboxes,primary SMTP addresses for each mailbox, usernames, aliases assigned tomailboxes, permissions for the mailboxes and its folders and subfolders(e.g. permission for User B to have read access to User A's calendar),collections of people that appear in an address book such as a list ofdistribution groups and their aliases, and a list of mailboxes that aremembers of the distribution groups.

Action 303 shows migration assistant storing the metadata in a singledata structure. For example, the collected inventory of business rulescan be stored in an in-memory data structure called an “instance of aclass.” This class instance can be serialized into an XML document byway of various software programming techniques, and saved to a standarddata file location that is available for programs running on a computer.

Action 304 shows migration assistant 124 sending the single datastructure to migration controller server 110. For example, the XML filecan then be sent to the migration controller server 110 via a webservice call (protocol used for communicating between two differentsystems), stored in a database, such as a cloud database, and thenreplicated in the destination system 118.

With this solution, the quality, accuracy and breadth of informationthat is migrated to the destination system 118 may be improved over whatwould be obtainable by using strictly remote access (i.e. without thesupport of the migration assistant 124).

For example, without migration assistant 124, an internet discoveryprocess could find all distribution group email addresses and who is inthose distribution groups, and those distribution groups could berecreated on the destination system 118 and any emails to thosedistribution groups would be delivered to the right people. With thesupport of the migration assistant 124 making queries, such as aPowerShell-based queries of the source email and user databases,however, more information may be obtained, e.g. the “friendly” name ofthe distribution group that users in the organization see may beobtained, as well as rules dictating whether or not people should beallowed to email the distribution group from outside the company. Assuch, the migration assistant 124 may provide a more thorough discoveryof information, which allows for a migration that, after completion, isless visible to users and requires less effort to make the migratedenvironment at the destination environment 130 appear and perform likethe original source environment 120. The source environment can comprisean email system and other environment around it, for example a directorysystem such as Active Directory. The queries may try to obtaininformation such as the number of accounts, number of mailboxes, detailsabout each account such as first name, last name, and phone number, theprimary email account.

Further, source system data that is available for collection via remoteaccess methods may be collected with higher speed and accuracy by themigration assistant 124, since it may directly query active directory122 and other sources on source system 136. Remote collection relies onthe quality of the protocols for the information, which may not havebeen designed to provide that information, and therefore may result inincomplete data transfer.

IV. Preparation of Migration Using Migration Assistant

The migration assistant can be used to operations to prepare for amigration of documents from a source system to a destination system. Forexample, the migration assistant can collect metadata about the sourcesystem, for a migration controller to analyze. The migration controllercan determine changes that are required at the source system. Themigration controller can generate the commands and send them to themigration assistant for implementing the changes to the source system.

A. Block Diagram

FIG. 4 shows a block diagram for using a migration assistant executingat a source system for a migration project according to embodiments ofthe present invention. FIG. 4 refers to certain elements from FIG. 1.

Action 401 shows an identifier that identifies a migration project beingsent from the migration assistant 124 to the migration controller server110. The identifier can identify the migration project that themigration assistant is to be used for. The migration controller servercan use the identifier to determine commands corresponding to themigration project to send to the migration assistant.

Action 402 shows migration assistant 124 querying source server 136 tocollect metadata from the source server, the metadata corresponding todocuments stored on the source server. The migration assistant can queryusing the first communication connection channel. In response to thequery, the source server may send back any metadata found. For example,the commands may comprise Powershell queries to the source system toobtain data and metadata pertaining to documents in a document server ofthe source system or directory data from a directory service.

Action 403 shows migration assistant 124 sending the collected metadatato the migration controller server. The metadata may include informationabout how many mailboxes are on a document server and details about eachmailbox, such as user information including first name, last name, phonenumber, email address, aliases, the amount of data stored in a mailbox,and other similar data. The migration controller server 110 can generateone or more commands based on the metadata sent to it. The commands maybe determined based on input from an operator at the migrationcontroller server 110, where the input may be received before or afterreceiving the metadata. For example, the user input can have previouslyspecifies an amount of time for the migration or a number of documentsto be transferred per stage. Migration controller server 110 can thenautomatically determine which accounts to migrate and which changes needto be made at the source server.

Action 404 shows sending any commands generated by migration controllerserver 110 to migration assistant 124. The commands can specify forexample which accounts are to be migrated. The commands can also specifywhich accounts need to be changed during or after a migration. Thecommands may specify changes to be made for the source system as part ofthe migration project. Examples of change commands are provided belowand can include disabling features and changing settings (e.g., links touser accounts).

Action 405 shows sending specified changes from migration assistant 124to source system 136. The specified changes can automatically preparethe source document server for the migration, e.g., in a process thatoccurs after the migration assistant is installed. The commands forexample, can specify forwarding of mail and data from one account toanother. A command can instruct a server to convert an on-premisesmailbox into an MEU.

Action 406 shows a confirmation message being sent from migrationassistant 124 to migration controller server 110. When the migrationchanges are completed, commands can be sent from the migration assistantto indicate completion of the changes needed for migration. In responseto the confirmation message, the migration controller server 110 canthen begin control of the migration, e.g., by sending commands to amigration engine.

B. Method

FIG. 5 is a flowchart of a method 500 of a migration process using amigration assistant according to embodiments of the present invention.Method 500 may be implemented by elements of a migration controllerenvironment, e.g., in communication with a migration assistant, as seenin FIG. 1.

At block 510, a migration assistant may be executed on a computer of asource system. The execution may start up the migration assistant toprepare it for a migration. The migration assistant will already beinstalled in the source environment. When installed, a unique identifieror product key that is associated with the migration assistant will havebeen generated.

At block 520, an identifier that identifies a migration project can besent, from the migration assistant to a migration controller server. Theidentifier can identify the migration project that the migrationassistant is to be used for. The migration controller server can use theidentifier to determine commands corresponding to the migration projectto send to the migration assistant. This identifier can be used as partof an authentication mechanism.

At block 530, a first communication connection between the migrationassistant and a source document server of the source system can beestablished. This first communication connection may be used by themigration assistant to collect relevant data and metadata from a sourcesystem of the source environment.

At block 540, the migration assistant using the first communicationconnection may query the source document server to collect data andmetadata from the source document server. The metadata may correspond todocuments stored on the source document server. Once the metadata isreceived, the migration controller server may generate the one or morecommands based on the metadata. The migration assistant may issuecommands, such as Powershell queries, to the source system to obtaindata and metadata pertaining to, for example, documents in a documentserver of the source system or directory data from a directory service.The queries may ask for information such as how many mailboxes are on adocument server and details about each mailbox such as the userinformation including first name, last name, phone number, emailaddress, aliases, the amount of data stored in a mailbox, and othersimilar data.

At block 550, a second communication connection between the migrationassistant and the migration controller server is established by themigration assistant using the identifier. This connection may beauthenticated using the identifier and possibly other factors, e.g., asdescribed above.

At block 560, the migration assistant can send, via the secondcommunication connection, the metadata to the migration controllerserver. Once the connection is established and authenticated, themigration assistant may send data and metadata collected to themigration controller server.

At block 570, the migration assistant can receive from the migrationcontroller server, one or more commands for the migration project. Theone or more commands can specify one or more changes to be made for thesource system as part of the migration project. The commands can specifyfor example which accounts are to be migrated. The commands can alsospecify which accounts need to be changed at various times through amigration.

At block 580, the migration assistant may implement the one or morecommands to make the specified changes to the source system. Thespecified changes can automatically prepare the source document serverfor the migration, e.g., in a process that occurs after the migrationassistant is installed. The commands may specify that mail is to beforwarded from one account to another. A command may instruct a serverto convert an on-premises mailbox into an MEU.

At block 590, the migration assistant can send a confirmation to themigration controller server, the confirmation stating that the specifiedchanges have been implemented. The confirmation can be conveyed in anysuitable manner. In various embodiments, the confirmation can be sentonly when the specified changes have been made, or may be sent at apredetermined time after the commands are received at block 570. Theconfirmation can always indicate a successful implementation of thechanges, or sometimes different status messages can be sent. Forexample, the confirmation can be a binary flag that indicates thesuccess or failure. Other embodiments can indicate varying levels ofpartial success for some commands or partial failure.

V. Service Call

In some embodiments, the migration assistant 124 may send a web servicecall to the migration controller server 110 to check if there are anycommands for the migration assistant 124 to perform (e.g. query theemail system for a list of all user mailboxes and their details and sendback to the migration controller). If there are one or more commands toperform, the migration controller server 110 may send the command(s) tothe migration assistant 124. If there are no commands to perform, themigration controller server 110 may send a message to the migrationassistant 124 reporting as such. This process may be repeated atpredefined intervals, e.g. once every minute.

Other examples of commands that might be sent to the migration assistant124 by the migration controller server 110 include, but are not limitedto: obtaining a list of all distribution groups and their membership,obtaining a list of all security groups and their membership, setting upa forwarding rule for a specific mailbox to forward mail to a specifiedexternal email address, and to convert an on-premises mailbox to a “mailenabled user” (MEU). This conversion of an on-premises mailbox to an MEUcan in effect delete the mailbox from the system. The MEU can be a useraccount in a directory service such as Active Directory that has ane-mail address associated with it, but has no mailbox on an on-premisesmail server, such as an Exchange server. A mail-enabled user can sendand receive e-mail using another messaging system, for example an Office365 system.

VI. Commands

In some embodiments, the commands that the migration controller server110 sends to the migration assistant 124 are managed and executed via aworkflow engine 116, which can comprise a server or part that can managethe order in which commands are sent out. Such commands may depend onthe nature of the migration. For example, some migrations of data from asource system 136 that serves a relatively small number of users may bedone most efficiently in a single pass or single stage (hereinafterreferred to as a “cutover migration”). On the other hand, migrations ofdata from a source system 136 that serves a relatively large number ofusers may be optimized by being performed in stages (hereinafterreferred to as a “staged migration”). In each of these cases, themigration assistant 124 may run different commands to optimize thedifferent types of migrations; a discussion of the commands that may berun in these two scenarios follows below.

A. Cutover Migration Commands

In some embodiments, the migration controller server 110 may send to themigration assistant 124 one or more commands to optimize a cutovermigration. These commands may include but are not limited to: collectbusiness rules, disable a feature of Microsoft Exchange 128 called“Outlook Anywhere®,” and reconfigure the source system's serviceconnection points (objects in Active Directory 122 that hold informationabout services and are hereinafter referred to as “SCPs”). Thesecommands are discussed in turn below.

FIG. 6 is a flow diagram of a method 600 for a cutover migrationaccording to various embodiments. Method 600 can be performed by amigration assistant pursuant to commands from a migration controller.

At block 610, business rules can be collected from a source server.Business rules can comprise all of the different configuration settingsthat may be in place on a source server. For example, aliases that havecertain rules on them so that emails get forwarded somewhere else in anorganization when they come in, distribution groups having one or moremembers in them. Business rules that may be collected can also include,but are not limited to, user mailboxes, primary SMTP addresses for eachmailbox, usernames, aliases assigned to mailboxes, permissions for themailboxes and its folders and subfolders (e.g. permission for User B tohave read access to User A's calendar), collections of people thatappear in an address book such as a list of distribution groups andtheir aliases, and a list of mailboxes that are members of thedistribution groups.

At block 620, the communications between the source server and a userare disabled. As the user has been migrated over to another service, thecommunication to the source server may no longer be needed. In doing so,the system can take care to change settings so that the connections arenot re-enabled.

For example, “Outlook Anywhere®” could be disabled. “Outlook Anywhere®”is a service that allows users to connect to the Exchange server 128from the internet. If users use Outlook Anywhere® during the latterstages of a migration, however, they will be directed to the wrongserver (i.e. a server at the source system 136), and they will notreceive the emails that are being sent to them. As such, in someembodiments the migration controller server 110 can send the migrationassistant 124 a command to connect to the primary Microsoft Exchangeserver 128 (which is Microsoft's® implementation of an email system)local to the source system 136 and disable Outlook Anywhere®. Bydisabling Outlook Anywhere® and stopping users from communicating withtheir old mailbox, the chance of incoming email being delivered to thewrong location may be reduced or eliminated. Some embodiments mayexecute this command to disable Outlook Anywhere® close to (e.g. withinfive minutes of) the specified final migration date and time (which maybe specified by a partner or customer) to reduce the risk of mail beingdelivered to the wrong location.

At block 630, the service connection points that store Internetaddresses that are provided to devices for connecting to the sourcedocument server are reconfigured to change how connections are made. Asan example, the SCP (service connection point) can be a piece ofinformation that a Microsoft Exchange server 128 stores in its databasewhich holds an internet URL, which when asked for, the Exchange server128 will provide to an end user's email system 132 (e.g. Outlook® ormobile device) which in turn is used by this email system to configureitself and connect to the email server.

In some embodiments, the migration controller server 110 may send themigration assistant 124 a command at or shortly after the finalmigration date and time to reconfigure the auto-discover address ofevery SCP (service connection point) that is local to the source system136; the migration assistant 124 may then execute this command. Thefinal migration date and time can refer to the date and time to completea migration. The Autodiscover address or URL can comprise an internetURL to negotiate a handshake.

A reason behind executing the command to reconfigure the Autodiscoveraddress of every SCP local to the source system 136 is as follows: aspart of a migration, the local email application communicates with amailbox at the destination system 118 of the migration (e.g. Office365®, Google®, etc.). The local email application, however, has amechanism to check the Autodiscover address of the source system's SCPsat intervals (e.g. every 30 minutes); if the Autodiscover address of theSCPs do not match the Autodiscover address associated with thedestination system 118 of the migration, then the local emailapplication will reconfigure itself to communicate with the mailbox onthe source system 136. If this occurs after the migration date and time,extra time and expense will be required to re-direct the email client tocommunicate with the new destination email system.

To remedy the above problem, in some embodiments the migration assistant124 may be commanded by the migration controller server 110 to connectto each client access server (known as “CAS”, a Microsoft® Server usedas a proxy for email clients to connect to, which in turn connects themto the email database) that it discovered earlier when collecting thebusiness rules, and update the SCP Autodiscover URL for each one so thatit matches the new destination system 118 of the migration. This may bedone manually or automatically, and preferably, immediately (i.e. withina few seconds) prior to the local email application being reconfiguredto communicate with the destination system 118, so that all subsequentchecks by the local email application on the Autodiscover address areless likely to encounter mismatched Autodiscover addresses, andtherefore less likelihood of reverting back to the mailbox on the sourcesystem 136.

B. Staged Migration Commands

In some embodiments, the migration controller server 110 may send to themigration assistant 124 one or more commands that can optimize a stagedmigration. One such command that the migration assistant 124 may carryout is to convert one or more mailboxes to “mail enabled users”(hereinafter referred to as “MEUs”). An MEU is an object in the Exchangeserver 128 that instructs Exchange 128 that the mailbox for a specificemail address is located at a location outside of its local ActiveDirectory environment 122.

FIG. 7 is a flow diagram of a method 700 of staged migration accordingto various embodiments. For each mailbox that the migration controllerserver 110 commands migration assistant 124 to convert to a MEU, thefollowing may be done by some embodiments. Method 700 can be performedby a migration assistant pursuant to commands from a migrationcontroller.

At block 710, the list of mailboxes to convert to an MEU is determined.As each mailbox that is part of a stage scheduled to be convertedfinishes its final synchronization with the mail server, the migrationcontroller server 110 may send the command to convert those mailboxes toMEUs. After the command is received by the migration assistant 124, itconnects to the Exchange server 128 local to the source system 136. Themigration assistant 124 gathers all of the email addresses associatedwith the mailbox to be converted.

At block 720, a mailbox that is to be converted to an MEU isdisassociated from the source server. The migration assistant 124 canthen disable the mailbox. The mailbox can be disassociated in a varietyof ways. For example, the migration assistant can send commands to themailbox or to the source server, or to both.

At block 730, an MEU object is created for the user account that waspreviously associated with a mailbox account on the source server. Oncethe MEU object is created, the user account can be changed to be an MEUaccount.

At block 740, any of the aliases that used to be on the mailbox areconverted to the MEU object. This can apply to any of the non-vanityaddresses and aliases that used to be on the mailbox account on thesource server.

At block 750, all email aliases that used to be on the mailbox arereassigned to the MEU object. The forwarding address of the MEU to theappropriate destination email address can be modified.

A reason the forwarding address is set to a different domain is that formany email systems, for each mailbox that is created, a unique emailaddress on that provider's domain is given. For example, a person, JohnDoe, who works at Company A and gets a mailbox from Provider X mightreceive the following email addresses: john.doe@companya.com andjohn.doe@companya.providerx.com. The latter is a unique address and isthe forwarding address that the migration assistant 124 assigns to theMEU that is created. This is done because if the former address wasassigned to the MEU, then Exchange 128 would not be able to deliver theemail to the appropriate mailbox on the destination system 118 becausethe Exchange server 128 would still be hosting email for the domain thatthe email address is a member of, so Exchange 128 would look internallyfor the mailbox.

After the MEU conversion commands are completed, the migration assistant124 may return a success/failure status message to the migrationcontroller server 110, and then returns to the service call processdescribed above.

For example, in a staged migration of 1000 mailboxes, there may be 100mailboxes in a stage that are scheduled to be migrated at 5 PM. At 5 PM,the final synchronization of those mailboxes is started. The migrationcontroller server 110 will not send the command to convert any mailboxeswhose synchronization has not finished; if the migration controllerserver 110 did send the command before the synchronization was finished,the synchronization would fail because the mailbox could be deleted ordeactivated at its source, making the mailbox no longer accessible.Therefore, if only one mailbox has finished the synchronization at thetime the migration assistant 124 polls the migration controller server110 for commands during its service call process, then the migrationcontroller server 110 will send the command to convert that mailbox, andonly that mailbox, to an MEU. And if multiple mailboxes have finishedtheir synchronization at the time of the service call, the migrationassistant 124 will be commanded by the migration controller server 110to convert those mailboxes to MEUs. This process is repeated until allmailboxes in the stage have been converted to MEUs.

The reason this command to convert the mailboxes to MEUs is carried outis similar to the reasoning behind the reconfiguration of the SCPs'Autodiscover URLs in the case of cutover migrations. If the mailbox isnot converted to an MEU, Outlook will be reconfigured to communicatewith the mailbox on the source system 136, rather than the desiredmailbox at the destination system 118, and a migration already inprogress may be disrupted. Mailboxes do not need to be converted to MEUsin cutover migrations, however, because changing the DNS record during acutover migration completely re-routes mail destined for the sourcesystem 136 to the destination system 118.

The sequencing and timing of the steps taken in the above-describedcommand sequence for some embodiments is important so that the MEUs arecreated correctly and mail flow will not be inhibited; other sequencesmay be used in other embodiments not described herein.

Accordingly, the migration assistant can be receive one or moreadditional commands at a later stage from the migration controllerserver, and then implement the one or more additional commands at thelater stage when the additional command(s) are received.

VII. File Migration

Some embodiments may be used for file migrations from a source system136 to a destination system 118. A file is another example of a documentthat may be migrated from a source system to a destination system. Anexample of how this may be done is as follows.

The migration controller server 110 sends a command to the migrationassistant 124 to get a list of all file servers in the source systemenvironment 120 and data related to those file servers. The migrationassistant 124 can crawl the network by communicating 126 with adirectory service such as Active Directory 122 to get a list of allservers, connects each of those servers to retrieve their filehierarchy, and retrieves the hierarchy of folders for all the servers onthe network. All of this data may be combined in a single document suchas an XML document and sent to the migration controller server 110.Partners and/or their customers may go to a centralized user interfacesuch as a user portal website, see all this information in the front endinterface 104, and specify which files should be migrated.

The migration controller server 110 may send another command, to migratesome or all of the hierarchy that was retrieved. The command includes alist of all the folders and subfolders that should be migrated, alongwith the location they should be migrated to. The migration assistant124 connects out to that server, and reads all the documents in thehierarchy and copies them up to the location specified by the migrationcontroller server 110.

The migration controller server 110 may send another command, to performsynchronization of the file structure/hierarchy. The migrationcontroller server 110 specifies the server and hierarchy to synchronize,and the destination system 118 to synchronize to. The migrationassistant 124 makes a comparison between the source environment 120 anddestination environment 130, and any deltas discovered are reconciled byeither re-copying the file or copying the new file to the destinationsystem 118.

The migration controller server 110 may send another command, directingthe migration assistant 124 on how much bandwidth should be used tomigrate files. Such bandwidth caps might depend on, for example, whenthe traffic is occurring: what hour of the day, and whether on a weekdayor a weekend.

VIII. Computer System

Any of the computer systems mentioned herein may utilize any suitablenumber of subsystems. Examples of such subsystems are shown in FIG. 8 incomputer apparatus 10. In some embodiments, a computer system includes asingle computer apparatus, where the subsystems can be the components ofthe computer apparatus. In other embodiments, a computer system caninclude multiple computer apparatuses, each being a subsystem, withinternal components.

The subsystems shown in FIG. 8 are interconnected via a system bus 75.Additional subsystems such as a printer 74, keyboard 78, storagedevice(s) 79, monitor 76, which is coupled to display adapter 82, andothers are shown. Peripherals and input/output (I/O) devices, whichcouple to I/O controller 71, can be connected to the computer system byany number of means known in the art such as input/output (I/O) port 77(e.g., USB, FireWire®). For example, I/O port 77 or external interface81 (e.g. Ethernet, Wi-Fi, etc.) can be used to connect computer system10 to a wide area network such as the Internet, a mouse input device, ora scanner. The interconnection via system bus 75 allows the centralprocessor 73 to communicate with each subsystem and to control theexecution of instructions from system memory 72 or the storage device(s)79 (e.g., a fixed disk, such as a hard drive or optical disk), as wellas the exchange of information between subsystems. The system memory 72and/or the storage device(s) 79 may embody a computer readable medium.Any of the data mentioned herein can be output from one component toanother component and can be output to the user.

A computer system can include a plurality of the same components orsubsystems, e.g., connected together by external interface 81 or by aninternal interface. In some embodiments, computer systems, subsystem, orapparatuses can communicate over a network. In such instances, onecomputer can be considered a client and another computer a server, whereeach can be part of a same computer system. A client and a server caneach include multiple systems, subsystems, or components.

It should be understood that any of the embodiments can be implementedin the form of control logic using hardware (e.g. an applicationspecific integrated circuit or field programmable gate array) and/orusing computer software with a generally programmable processor in amodular or integrated manner. As used herein, a processor includes asingle-core processor, multi-core processor on a same integrated chip,or multiple processing units on a single circuit board or networked.Based on the disclosure and teachings provided herein, a person ofordinary skill in the art will know and appreciate other ways and/ormethods to implement embodiments using hardware and a combination ofhardware and software.

Any of the software components or functions described in thisapplication may be implemented as software code to be executed by aprocessor using any suitable computer language such as, for example,Java, C, C++, C#, Objective-C, Swift, or scripting language such as Perlor Python using, for example, conventional or object-orientedtechniques. The software code may be stored as a series of instructionsor commands on a computer readable medium for storage and/ortransmission, suitable media include random access memory (RAM), a readonly memory (ROM), a magnetic medium such as a hard-drive or a floppydisk, or an optical medium such as a compact disk (CD) or DVD (digitalversatile disk), flash memory, and the like. The computer readablemedium may be any combination of such storage or transmission devices.

Such programs may also be encoded and transmitted using carrier signalsadapted for transmission via wired, optical, and/or wireless networksconforming to a variety of protocols, including the Internet. As such, acomputer readable medium according to various embodiments may be createdusing a data signal encoded with such programs. Computer readable mediaencoded with the program code may be packaged with a compatible deviceor provided separately from other devices (e.g., via Internet download).Any such computer readable medium may reside on or within a singlecomputer product (e.g. a hard drive, a CD, or an entire computersystem), and may be present on or within different computer productswithin a system or network. A computer system may include a monitor,printer, or other suitable display for providing any of the resultsmentioned herein to a user.

Any of the methods described herein may be totally or partiallyperformed with a computer system including one or more processors, whichcan be configured to perform the steps. Thus, embodiments can bedirected to computer systems configured to perform the steps of any ofthe methods described herein, potentially with different componentsperforming a respective steps or a respective group of steps. Althoughpresented as numbered steps, steps of methods herein can be performed ata same time or in a different order. Additionally, portions of thesesteps may be used with portions of other steps from other methods. Also,all or portions of a step may be optional. Additionally, any of thesteps of any of the methods can be performed with modules, circuits, orother means for performing these steps.

The specific details of particular embodiments may be combined in anysuitable manner. However, other embodiments may be directed to specificembodiments relating to each individual aspect, or specific combinationsof these individual aspects.

The above description of exemplary embodiments has been presented forthe purposes of illustration and description. It is not intended to beexhaustive or to limit the invention to the precise form described, andmany modifications and variations are possible in light of the teachingabove. The embodiments were chosen and described best explain principlesand their practical applications.

A recitation of “a”, “an” or “the” is intended to mean “one or more”unless specifically indicated to the contrary. The use of “or” isintended to mean an “inclusive or,” and not an “exclusive or” unlessspecifically indicated to the contrary.

All patents, patent applications, publications, and descriptionsmentioned here are incorporated by reference in their entirety for allpurposes. None is admitted to be prior art.

What is claimed is:
 1. A method comprising: receiving, from a migrationassistant being executed on a source system, an identifier thatidentifies a migration project for migrating documents from the sourcesystem to a destination system; facilitating establishing, using theidentifier, a communication link with the migration assistant; sending,to the migration assistant, an instruction to collect metadata from asource document server of the source system, the metadata correspondingto documents stored on the source document server; receiving, from themigration assistant over the communication link, the metadata collectedby the migration assistant according to the instruction; generating oneor more commands based on the metadata, the one or more commandsspecifying changes to be made for the source system as part of themigration project; sending, to the migration assistant over thecommunication link, the one or more commands for the migration project;and receiving, from the migration assistant over the communication link,a confirmation that the specified changes have been implementedaccording to the one or more commands.
 2. The method of claim 1, whereinthe identifier is received after the migration assistant is installed onthe source system, and wherein the identifier includes a registrationcode entered at a user interface of the migration assistant.
 3. Themethod of claim 2, further comprising: using the identifier toauthenticate the migration assistant and determine the migrationproject; and sending, to the migration assistant over the communicationlink, an authentication response that the migration assistant has beenauthenticated.
 4. The method of claim 1, wherein the metadata specifiesa number of user accounts in the source document server and identifyinginformation for each user account.
 5. The method of claim 1, wherein theinstruction specifies that the metadata is to include distributiongroups and their membership and security groups and their membership. 6.The method of claim 1, wherein the source document server is an e-mailserver, and wherein the instruction specifies to collect rules about anoperation of the source document server, and wherein the rules arerelated to one or more of: user mailboxes, primary SMTP address for eachmailbox, usernames, aliases assigned to mailboxes, permissions for themailboxes and its folders and subfolders, a list of distribution groupsand their aliases, a list of mailboxes that are members of thedistribution groups, mailbox permissions, and user information.
 7. Themethod of claim 6, further comprising: receiving, from the migrationassistant over the communication link, a data file comprising the rules.8. The method of claim 7, wherein the rules are serialized in the datafile, and wherein the data file is an XML file.
 9. The method of claim1, wherein a plurality of documents to be migrated include emails of aspecific mailbox on the source system, wherein the one or more commandsinclude: a disassociation of the specific mailbox from the sourcesystem; and a forwarding rule for the specific mailbox to forward emailto a specified external email address associated with the destinationsystem.
 10. The method of claim 9, wherein the one or more commandsfurther include: a conversion of the specific mailbox to have a statusthat the specific mailbox for a specific email address is located at alocation outside of its local environment.
 11. The method of claim 1,wherein the one or more commands are for a cutover migration or are fora staged migration.
 12. The method of claim 1, wherein the one or morecommands include: collecting business rules specifying which users canaccess which documents of the source document server.
 13. The method ofclaim 1, wherein the one or more commands include a command to disablecommunication of a user with the source document server.
 14. The methodof claim 1, wherein the one or more commands include a command toreconfigure a plurality of service connection points that store Internetaddresses that are provided to devices for connecting to the sourcedocument server.
 15. A computer product comprising a non-transitorycomputer readable medium storing a plurality of instructions forcontrolling a computer system of a source system, the instructionscomprising: receiving, from a migration assistant being executed on asource system, an identifier that identifies a migration project formigrating documents from the source system to a destination system;facilitating establishing, using the identifier, a communication linkwith the migration assistant; sending, to the migration assistant, aninstruction to collect metadata from a source document server of thesource system, the metadata corresponding to documents stored on thesource document server; receiving, from the migration assistant over thecommunication link, the metadata collected by the migration assistantaccording to the instruction; generating one or more commands based onthe metadata, the one or more commands specifying changes to be made forthe source system as part of the migration project; sending, to themigration assistant over the communication link, the one or morecommands for the migration project; and receiving, from the migrationassistant over the communication link, a confirmation that the specifiedchanges have been implemented according to the one or more commands. 16.The computer product of claim 15, wherein the identifier is receivedafter the migration assistant is installed on the computer of the sourcesystem, and wherein the identifier includes a registration code enteredat a user interface of the migration assistant, and wherein theinstructions further comprise: using the identifier to authenticate themigration assistant and determine the migration project; and sending, tothe migration assistant over the communication link, an authenticationresponse that the migration assistant has been authenticated.
 17. Thecomputer product of claim 15, wherein the instructions specifies thatthe metadata is to include distribution groups and their membership andsecurity groups and their membership.
 18. The computer product of claim15, wherein the source document server is an e-mail server, and whereinthe instructions specify to collect rules about an operation of thesource document server, wherein the instructions further comprise:storing the rules into a data file.
 19. The computer product of claim15, wherein a plurality of documents to be migrated include emails of aspecific mailbox on the source system, wherein the one or more commandsinclude: a disassociation of the specific mailbox from the sourcesystem; a forwarding rule for the specific mailbox to forward email to aspecified external email address associated with the destination system;and a conversion of the specific mailbox to have a status that thespecific mailbox for a specific email address is located at a locationoutside of its local environment.